home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94b.txt
/
000024_icon-group-sender _Mon Aug 29 23:46:57 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-09
|
1KB
Received: by cheltenham.cs.arizona.edu; Tue, 30 Aug 1994 05:15:04 MST
To: icon-group-l@cs.arizona.edu
Date: 29 Aug 1994 23:46:57 -0400
From: nmw@ios.com (Nick Williams)
Message-Id: <33ua3h$51h@ios.com>
Organization: Internet Online Services
Sender: icon-group-request@cs.arizona.edu
References: <Cv9Jvr.AC4@world.std.com>, <33smt8$meg@ios.com>, <1994Aug29.223512.12423@kf8nh.wariat.org>
Subject: Re: Icon - still alive??
Errors-To: icon-group-errors@cs.arizona.edu
In article <1994Aug29.223512.12423@kf8nh.wariat.org>,
Brandon S. Allbery <bsa@kf8nh.wariat.org> wrote:
>Binary file I/O for non-character data would be nice. Or, alternatively,
>functions akin to Perl's pack()/unpack(). I have several Perl scripts I would
>happily move to Icon if I didn't have to manipulate C (short) and (long)
>values in native format (no, I don't get to set the format of the files).
I thought reads() was meant to be used for binary data, am I wrong? If
characters in Icon can be treated as plain bytes then pack()/unpack()
type procedures could be built upon reads()/writes().
>++Brandon
>--
>Brandon S. Allbery KF8NH [44.70.4.88] bsa@kf8nh.wariat.org
>Linux development: iBCS2, JNOS, MH
>Daily dreading Nehemiah Scudder^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^HRush Limbaugh
Nick